docs(ledger): record open-PR babysit sweep outcomes by BigSimmo · Pull Request #1172 · BigSimmo/Database

BigSimmo · 2026-07-24T17:04:26Z

Summary

Fix cross-mode search performance findings: prescribing catalogue debounce/abort/fields=index, differentials abort/debounce, universal documents typeahead soft-timeout (750ms), shared (search-app) shell to avoid composer remount, and Answer rate-limit in-memory fallback outside production.
Fix Bugbot regressions: shared-shell pathname navigation (/services → /dsm) syncs searchMode during render (no stale-mode paint) even when the query string is unchanged; extracted ClinicalDashboard lazy imports to stay under the maintainability budget.

RAG impact: no retrieval behaviour change — typeahead documents domain timeout and shell URL sync only; ranking formulas and full /api/search retrieval path unchanged.

Verification

npm run verify:pr-local — focused Vitest on touched sources (362) plus api-rate-limit / search-shell / universal / route / site-map suites green; docs:check-index OK
UI verification not run: full verify:ui not required for this pass; mode-home smoke via npm run ensure returned HTTP 200 for /, /services, /dsm, /documents/search, /therapy-compass, /?mode=prescribing, and /api/answer/stream returned 200 after the rate-limit fallback fix
Verification not run: eval:retrieval:latency / soak / live OpenAI canary — approval-gated provider work; not needed for timeout-only typeahead change

Risk and rollout

Risk: medium — shared layout remount change and rate-limit fallback behaviour in non-production; production Answer/upload still fail closed when the durable limiter is unavailable
Rollback: revert this PR; mode routes return to per-segment GlobalSearchShell layouts and prior timeout/fallback behaviour
Provider or production effects: None

Clinical Governance Preflight

Source-backed claims still require linked source verification before clinical use
No patient-identifiable document workflow was introduced or expanded without explicit governance approval
Supabase target remains [REDACTED] ([REDACTED])
Service-role keys and private document access remain server-only
Demo/synthetic content remains clearly separated from real clinical sources
Source metadata, review status, and outdated/unknown-source behavior remain conservative
Deployment classification/TGA SaMD impact was checked when clinical decision-support behavior changed

Notes

Prescribing list rows keep the full catalogue payload so Safety/Monitoring filters and patient alerts still see section-derived signals; keystroke storms are controlled by debounce + abort. fields=index remains for identity-only consumers (cross-mode links).
Live hybrid RPC cold tails remain a separate approval-gated follow-up.

#1167 #1169 #1170 Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

supabase · 2026-07-24T17:04:32Z

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

coderabbitai · 2026-07-24T17:04:32Z

Warning

Review limit reached

@cursor[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 9168d323-7a70-438d-a71b-c400eca83eae

📥 Commits

Reviewing files that changed from the base of the PR and between c4ed151 and 1a7c636.

📒 Files selected for processing (1)

docs/branch-review-ledger.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch cursor/babysit-sweep-72ec

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

…72ec Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

Merged origin/main into remaining behind/dirty PR heads so every open PR is MERGEABLE with behind=0. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

Remove the second identical PR #1170 ledger record so check:branch-review-ledger passes. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

…72ec Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

Merged origin/main into every open PR head so all are current with main. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

Remove duplicate ledger records so check:branch-review-ledger passes after the conflict sync. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

Add a main-push workflow and local helper that update behind PR heads so GitHub stops falsely marking the queue CONFLICTING/DIRTY after each land. Bump postcss to a non-vulnerable release so Safety npm audit stays green.

…72ec

docs(ledger): record babysit sweep for PRs #1124 #1131 #1146 #1157 #1162

e27e066

#1167 #1169 #1170 Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

cursoragent and others added 12 commits July 24, 2026 17:13

Merge branch 'main' into cursor/babysit-sweep-72ec

b527a15

Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

docs(ledger): record open-PR conflict-resolution sweep and #1162 Bugbot

a5ca2ad

Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

Merge branch 'main' into cursor/babysit-sweep-72ec

0e30922

Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

docs(ledger): record #1162 conflict resolution and Bugbot outcome

a0c06d7

Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

Merge remote-tracking branch 'origin/main' into cursor/babysit-sweep-…

f6b7c31

…72ec Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

docs(ledger): record open-PR conflict sync (all mergeable)

54308bb

Merged origin/main into remaining behind/dirty PR heads so every open PR is MERGEABLE with behind=0. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

docs(ledger): drop exact duplicate #1170 review row

020859b

Remove the second identical PR #1170 ledger record so check:branch-review-ledger passes. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

Merge remote-tracking branch 'origin/main' into cursor/babysit-sweep-…

eae3dbf

…72ec Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

docs(ledger): record open-PR conflict sync for 22 PRs

d3b98f1

Merged origin/main into every open PR head so all are current with main. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

docs(ledger): drop exact duplicate review rows

e2bb965

Remove duplicate ledger records so check:branch-review-ledger passes after the conflict sync. Co-authored-by: BigSimmo <BigSimmo@users.noreply.github.com>

fix: auto-sync open PR branches and clear postcss audit

581febd

Add a main-push workflow and local helper that update behind PR heads so GitHub stops falsely marking the queue CONFLICTING/DIRTY after each land. Bump postcss to a non-vulnerable release so Safety npm audit stays green.

Merge remote-tracking branch 'origin/main' into cursor/babysit-sweep-…

681e628

…72ec

cursor Bot marked this pull request as ready for review July 24, 2026 19:15

Merge cursor/pr-queue-hygiene-72ec for postcss audit + PR branch sync

25e9861

cursor Bot enabled auto-merge (squash) July 24, 2026 19:17

Merge remote-tracking branch 'origin/main' into cursor/babysit-sweep-…

1a7c636

…72ec

cursor Bot merged commit 0a8dfdd into main Jul 24, 2026
18 checks passed

cursor Bot deleted the cursor/babysit-sweep-72ec branch July 24, 2026 19:26

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

docs(ledger): record open-PR babysit sweep outcomes#1172

docs(ledger): record open-PR babysit sweep outcomes#1172
cursor[bot] merged 15 commits into
mainfrom
cursor/babysit-sweep-72ec

BigSimmo commented Jul 24, 2026 •

edited by github-actions Bot

Loading

Uh oh!

supabase Bot commented Jul 24, 2026

Uh oh!

coderabbitai Bot commented Jul 24, 2026 •

edited

Loading

Review limit reached

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

BigSimmo commented Jul 24, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Verification

Risk and rollout

Clinical Governance Preflight

Notes

Uh oh!

supabase Bot commented Jul 24, 2026

Uh oh!

coderabbitai Bot commented Jul 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review limit reached

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

BigSimmo commented Jul 24, 2026 •

edited by github-actions Bot

Loading

coderabbitai Bot commented Jul 24, 2026 •

edited

Loading